Add Spec Trace extension to community catalog#2527
Conversation
mnriem
left a comment
There was a problem hiding this comment.
Please resolve conflicts
Note going forward adding/updating an extension please create an issue using the 'Extension Submission' template.
There was a problem hiding this comment.
Pull request overview
Adds the Spec Trace community extension to Spec Kit’s discovery surfaces (community catalog JSON + README table), making it easier for users to find and reference the extension for requirement→test traceability reporting.
Changes:
- Added a new
traceentry toextensions/catalog.community.json(including metadata, tags, and download URL) and bumped the catalogupdated_at. - Added a new “Spec Trace” row to the README Community Extensions table in alphabetical order.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds the “Spec Trace” entry to the Community Extensions table. |
| extensions/catalog.community.json | Adds the trace extension metadata and updates updated_at. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
|
Please address Copilot feedback |
|
Conflicts resolved in 71300c4 clean diff now (README +1, catalog +32). Thank you for the heads-up about the Extension Submission template I'll absolutely follow that process for all future extensions and updates going forward. Sorry for the extra work this caused; I appreciate the patience . |
|
Please address Copilot feedback |
The /speckit.trace.build command writes .specify/trace.md, so the catalog row's Effect column was wrong. Aligning with the extension's documented behavior.
# Conflicts: # README.md
|
Please address Copilot feedback. Note that huge table of community extensions in the README.md has moved to docs/community/extensions.md hence why it is asking you to list it there |
The public community extensions table moved from README.md to docs/community/extensions.md per the repo convention documented in .github/skills/add-community-extension/SKILL.md. Adding the Spec Trace row alphabetically between Spec Sync and Spec Validate so the doc stays in sync with the catalog entry already added.
|
Please address Copilot feedback |
Adds Spec Trace to the community catalog — a build-time requirement → test traceability extension.
/speckit.trace.buildparsesspec.mdfor REQ-XXX tokens and the test suite for the same tokens, then writes.specify/trace.mdcontaining a coverage matrix. Companion commands:/speckit.trace.gaps— list requirements with zero matching tests/speckit.trace.orphans— list tests that do not anchor to any REQ/speckit.trace.report— human-readable summaryEffect is Read+Write (because
trace.buildwrites.specify/trace.md).Changes
extensions/catalog.community.json— new"trace"entry, alphabetically placed betweentoken-analyzerandv-model.docs/community/extensions.md— new row added alphabetically betweenSpec SyncandSpec Validate. (This isthe current location of the public community extensions table; the README table was migrated here per repo convention
documented in
.github/skills/add-community-extension/SKILL.md.)Extension repo
Source: https://github.com/Quratulain-bilal/spec-kit-trace
Release: https://github.com/Quratulain-bilal/spec-kit-trace/releases/tag/v1.0.0
License: MIT
Verification
python -m json.tool extensions/catalog.community.jsonpasses — valid JSON.catalog.community.jsonanddocs/community/extensions.md.specify extension add trace --from <release-url>; all four commands execute withouterrors against a project with
spec.mdcontaining REQ-XXX tokens.Read+Write, sincetrace.buildwrites.specify/trace.md).